search

ericabouaf / wireit

A javascript wiring library to create web wirable interfaces for dataflow applications, visual programming languages or graphical modeling.
http://neyric.github.io/wireit/docs/
Other
520 stars 90 forks source link

default composite modules and accordion category blocks #28

Open DerManoMann opened 14 years ago

DerManoMann commented 14 years ago

I am in the process of upgrading my app to the edge branch and there are a couple things come up: a) I don't need the composite editors default modules and the only way to get rid seems to subclass, override buildModulesList() and set modules = [] This is a bit of a pain - due to the way things get called in the constructors. NOTE: We are using a custom load script to load modules remotely b) Corresponding to (a), I would like to get rid of the Main module category. However, the category specific id is only on the content block of the accordion code, so there is no way to create a CSS rule to hide it.

Generally I do have problems with the way defaults are set in the actual code, not the demo scripts. Also, the Main category accordion. Perhaps there should be an easier way to set/disable defaults? Another thing is that for 'Main' the css id is 'module-category-main' and the title 'Main' whereas for dynamically created categories both is lower case. I guess there is a fundamental issue using content for csss ids. What about translations - there would have to be CSS rules for each language...

Otherwise things are looking a lot rosier, IMHO.

ericabouaf commented 14 years ago

Hi,

I'm glad you tried the edge branch ! Lot of features are still unstable and need more work. I'm currently working on documentation so it's not going fast...

a) Are you using the "ComposableWiringEditor" plugin ? Because the "classic" editor doesn't add any module by default. Try to remove references to the ComposableWiringEditor plugin.

b) I'll try to make the module categories optional. I think it should be configurable in the language definition. We might also add custom CSS classes in the module definitions. It will be more verbose, but will prevent the issue you ran into.

DerManoMann commented 14 years ago

a) Yes I am using it. I was wondering myself why :) I guess it happened when I started working with the jsBox example... b) It kind of works for me - I only have to modules that are affected by that and the resulting class is unique, so I can handle that even though it is not idea.

Ta, mano