Re: Adding tag references and other suggestions

Gerald Bauer wrote:
> Hi Anakreon Mejdi,
> 
>   I hope you don't mind to answer in public so other
> can join the discussion and learn from your insights
> and suggestions.
Not at all.
> 
> 
>>There are a few things I noticed during the
>>development.
>>1)For a strange reason the Toolbar separators where
>>not painted.
> 
> 
>   Well, I guess they are invisible by default or it
> might be a bug. 
> 
>   I will check in a todo list so we can keep track of
> issues and make sure they don't get lost.
> 
>   Noone seems to like to use the "standard"
> sourceforge issue/bug tracking system. I guess it's
> just to heavy-weight and too much hassle. What's your
> opinion?
> 
>   As another light-weight alternative I hope to have a
> Wiki Wiki up and running in a couple of weeks.
> 
> 
I have used to report bugs on some cases for jEdit.
It would b egood if most of the users and developers use the
same mechanism to report bugs.
It would be better if we used the sourceforge system

>>2)The usage of many files is very usefull
>>techique.But this technique is 
>>limited by the fact that some tags can only exist
>>inside other tags.
>>I wanted to add a status bar in the window, which
>>can only exist inside 
>>a window tag.I placed it inside a window tag but if
>>I wanted to see the 
>>rest of components inside the window I should place
>>them inside the 
>>window tag.
>>In my opinion it would be more practical if I could
>>refer to those 
>>components in some whay, instead of putting the xml.
>>For example:
>><window ..attributes>
>>	<ref id="toolbarID" />
>>	<ref id="mainBoxId" />
>>	.. tags inside ..
>></window>
>>The requirement for a status bar to exist inside of
>>a window should not 
>>exist.Instead, a status bar can be inside of a xul
>>tag, but should be 
>>ignored if is not referenced inside a window tag.
> 
> 
>   I agree that makes perfect sense. In the meantime
> you can try to use Velocity's #include directive to
> split up your all-in-one file.
Yes, as a quick workaround I guess I could.
> 
>   As syntax I suggest using "typesafe" references e.g.
> 
>   <toolbar ref="toolbarID" />
>   <statusbar ref="mainBoxId" />
I prefer this one.The user will need to know less tags.
>    or
>   <toolbarref id="toolbarID" />
>   <statusbarref id="mainBoxId" />
> 
>   instead of generic
> 
>    <ref id="toolbarID" />
>    <ref id="mainBoxId" />
> 
>>It should be an error if is inside an other element
>>except <window> or 
>><xul> or is referenced inside other elements except
>><window>
>>Rules alike the one mentioned for statusbar should
>>exist for other 
>>elements acordingly.
> 
> 
>    I agree using references makes sense for almost all
> tags and needs to get added to the Luxor kernel.
> 
> 
>>3)Should implement a style attribute:visibility.
>>This will be very usefull in declaring components
>>which will later be 
>>shown programmaticly(by beanshell for example)
> 
> 
>    Yeah. Makes sense. You might wonna check out the
> proper "standard" CSS style property name and use it.
>  
> 
>>What do you think?
> 
> 
>   Great suggestions. You're more than welcome to
> beef-up Luxor and add the missing pieces to the main
> trunk. 
> 
>   - Gerald
> 
In the next days, if I manage finding some spare time, I will start the 
implementation of references.

Anakreon



-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54