One solution
It is needed to change the following:
1. the type of setProperty can only have one type not a list of types
for example if a label has a text string and a function retrieving
the text string as in localisation. QxExtend class.
2. then the rendering of all widgets mu
I hope this works in your machines right out of the box.
Known general problems:
1. add a QxListView
It is already a very buggy class, and together with QxSplitPane it
becomes worse.
2. add a QxTree
The ugly scrollbar does not disappear when moving the splitter.
Additionally, in exam
Hi Olli,
I think this will definetely be needed. The application should only load
what it needs to speed loading.
May I suggest that you split your class into two parts.
1) Will parse JS files to generate XML info about what is needed
2) Will take the XML info and generate a combined JS file in
Ben,
This sounds very interesting. Any chance you can share the code?
Something like this will be an essential part of a comprehensive PHP/qooxdoo
framework longterm.
Christoph
--
View this message in context:
http://www.nabble.com/PHP-Framework-t1366771.html#a3716395
Sent from the qooxdoo-deve
Well I think the backend should be pluggable so you can use XML, JSON,
QxBuilder, JS, PHPTAL, Smarty etc...
First thing we need to do is to get a standard communication layer defined
that can transport all this to load templates, definitions or trigger php
business logic. We can then plug in hand
> Why don't just start?
> I think there are (at least some) people on this list who would be
> more than willing to answer questions as you go through the
> re-implementing.
I am going to. At the moment I am trying to gather more information on what
has been done for some of the components I will
I really like QxBuilder. Its one great solution to not have to deal with
javascript. Only problem with it is that nobody seems to know a lot about it
or is working on expanding its functionality.
XSL is a great solution if you have the know-how on how to write the
transformations. It can get ver
Hi Christian,
This looks very interesting. Its great to see someone elses take on a
general framework. I have been working on a general framework for PHP for
the last few years and will be releaseing some components under the LGPL
soon. My main focus was re-usable low-level components that any a
Thanks, Ralf! That's the information I needed to get
rolling.
For those like me who are trying to get started, you
can put Ralf's example into the First Step directory
structure by changing:
imageCorePath : "../qooxdoo/images",
imageIconPath : "../qooxdoo/themes/icons",
imageWidgetPath : "../qoo
setAlias and getAlias are today limited to only one alias each. As it is
needed in many cases, I have extended the class by the attached patch
and propose the change. The syntax is now of two ways:
QxSplitPane.addProperty({ name : "leftWidget", getAlias : "getTopWidget",
setAlias : "setTopWidget"
Just for you to know: I only started with qooxdoo a few weeks before you
- so whatever I might suggest - there could well be a more expert way to
do things...
afaik there is no ide.
I have started experimenting by building my own simple page template and
then -bit by bit- extracting the essent
11 matches
Mail list logo
