RE: Using flow layout

So all 'custom' attributes turn into client properties right?  Aka, if a method cannot be found to call with the value in the tag, it turns into a custom property.

I just want the engine to be more extensible, and right now it seems like the engine is not very customizable without rewriting it.  Like what if you wanted to add another attribute that was handled the same way as the action attribute.  Where the client object is queried for an Action object (or any object) by using reflection rather then having to hardcode things in the XML?

So you could say this...
<frame bounds="frameBounds">
...
</frame>

and in your client object do this...
class Client {
public Rectangle frameBounds; // loaded from a config file before rendering of GUI.
}

One can kind of do this by overriding the setClientProperty method of a custom tag and then processing it there, but one still doesn't have access to the client object, nor is it a very good extension mechanism as you have to then extend all of the objects you want your attribute tag to effect.

Or am I the only one that wants the ability to do this?

cheers,
Steve


-----Original Message-----
From: Wolf Paulus [mailto:[email protected]]
Sent: Wednesday, December 03, 2003 2:12 PM
To: List for Users of Carlsbad Cubes' Technologies and Products
Subject: Re: [Forum] Using flow layout


Look at the sample code:

I.e.
swixml/samples/ClientAttr.java
swixml/xml/clientattr.xml

/**
  * The ClientAttr shows in the usage of client attributes in swixml 
tags.
  *
...


On Dec 3, 2003, at 1:58 PM, <[email protected]> wrote:

> What about custom attributes?  Is Swixml going to have a way to add 
> custom attributes in a similar way as custom tags?
>
> -----Original Message-----
> From: Wolf Paulus [mailto:[email protected]]
> Sent: Wednesday, December 03, 2003 10:26 AM
> To: List for Users of Carlsbad Cubes' Technologies and Products
> Subject: Re: [Forum] Using flow layout
>
>
> Steve,
> This  is not entirely true. You can have custom LayoutManagers but need
> to register them in the TabLibrary. Moreover, you would have to write a
> Converter.
>
> Anyway, it has been widely recognized that the way layouts are handled
> in Swixml is far from optimal and the 1st release of Swixml 2 will have
> layouts promoted from an attribute to a tag.
>
> Please also look at Swixml web site, for some newly added sample.
>
>
> On Dec 3, 2003, at 9:10 AM, <[email protected]> wrote:
>
>> But you can't extend the layout system that Swixml uses to use your
>> own custom layout managers without changing the core code.  So you are
>> stuck with only using the swing layouts.
>>
>> -----Original Message-----
>> From: kate rhodes [mailto:[email protected]]
>> Sent: Wednesday, December 03, 2003 6:25 AM
>> To: List for Users of Carlsbad Cubes' Technologies and Products
>> Subject: Re: [Forum] Using flow layout
>>
>>
>> Unlike Thinlet SWIXML doesn't do it's own layout system. It uses Swing
>> classes for everything. It supports it exactly as well as the version
>> of
>> java you are using supports it.
>>
>>
>>
>> You can use ANY Swing layout you want. There aren't tags for them but
>> there is nothing to stop you from applying a layout in java to the
>> objects generated by SWIXML.
>>
>> There is no "best layout". You use whatever layout is most appropriate
>> to the needs of your interface.
>>
>> again... swixml DOES NOT have ANY layout managers of it's own. It uses
>> the layout managers in Swing. All SWIXML does is map XML to Swing
>> objects and instantiate those Swing objects with the attributes
>> specified in your XML via getters and setters.
>>
>> -Kate
>>
>> [email protected] wrote:
>>
>>>
>>>
>>> Hi,
>>>    I had used thinlet for a quite a while and when i started using
>>>    swixml i find that the support for flow layout is not that great 
>>> in
>>> swixml.
>>>
>>>     can anyone suggest what is the best layout to use with swixml
>>>      and can i use flow layout the same way as i do in thinlet.
>>>
>>> Regards,
>>> Akhil
>>>
>>> "DISCLAIMER: This message is proprietary to Hughes Software Systems
>>> Limited
>>> (HSS) and is intended solely for the use of the individual to whom it
>>> is
>>> addressed. It may contain  privileged or confidential information and
>>> should not be circulated or used for any purpose other than for what
>>> it is
>>> intended. If you have received this message in error, please notify
>>> the
>>> originator immediately. If you are not the intended recipient, you 
>>> are
>>> notified that you are strictly prohibited from using, copying,
>>> altering, or
>>> disclosing the contents of this message. HSS accepts no
>>> responsibility for
>>> loss or damage arising from the use of the information transmitted by
>>> this
>>> email including damage from virus."
>>>
>>>
>>> _______________________________________________
>>> Forum mailing list
>>> [email protected]
>>> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
>>>
>>>
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Forum mailing list
>> [email protected]
>> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
>>
>> _______________________________________________
>> Forum mailing list
>> [email protected]
>> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
>>
>>
>
>
> _______________________________________________
> Forum mailing list
> [email protected]
> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
>
> _______________________________________________
> Forum mailing list
> [email protected]
> http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com
>
>


_______________________________________________
Forum mailing list
[email protected]
http://carlsbadcubes.com/mailman/listinfo/forum_carlsbadcubes.com