One of the goal of Spec is to be portable.
But sadly, I am not an engineer working full time of Spec.
Right now I have priorities which slow down Spec improvements.
Yes and these priorities are important for you and for us as well. We want you
to have great grades!
Now we will see and
On Sat, Oct 13, 2012 at 1:43 AM, Igor Stasenko siguc...@gmail.com wrote:
Pavel, since i am potential user of Spec, i would like to know more details.
I know it takes more time to explain what exactly you don't like and
propose better alternative,
instead of just generic i don't like it.
Well,
Pavel
do you know VW spec, it is an array of symbol and spec is the same.
We should change the api at some point.
The point is that you do not code it by hand but that tools generate them.
Now we are not to the point where a tools can generate them.
But for us the OB is not the way to go
Igor wrote:
Anyways, UI stuff is tend to be complex no matter how nicely you wrap
it.. because it is UI.
I'd have to disagree there. Building UIs with Glamour is easy. I'd say Spec is
simply
at too low an abstraction level for most UI work. We might need a different
abstraction
for different
On 11.10.2012 23:11, Benjamin wrote:
On Oct 11, 2012, at 11:04 PM, Pavel Krivanek wrote:
Unfortunately it is not only about a layer between Morphic and Spec.
Whole Spec design is greatly conforming to Morphic. Check out Spec
definitions, they look almost like transcription of Morphic calls
Feel free to use this representaion instead:
{#ComposableSpec. #add:. {{#ComposableSpec. #add:. {#(#model #browseModel).
#layout:. {#FrameLayoutSpec. #fractions:offsets:. (0@0) corner: ((1/5)@1).
(0@0) corner: (0@0)}}. #add:. {#(#model #sendersModel). #layout:.
{#FrameLayoutSpec.
What about proper formatting? :-)
--Hannes
On 10/12/12, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote:
Feel free to use this representaion instead:
{#ComposableSpec. #add:. {{#ComposableSpec. #add:. {#(#model #browseModel).
#layout:. {#FrameLayoutSpec. #fractions:offsets:. (0@0)
Trust me, even with the nicest formatting, it's not something that you want to
read, or to write...
Here the formatting is bad because this code is generated by the SpecLayout
object.
Ben
On Oct 12, 2012, at 2:40 PM, H. Hirzel wrote:
What about proper formatting? :-)
--Hannes
On
On Thu, Oct 11, 2012 at 11:11 PM, Benjamin
benjamin.vanryseghem.ph...@gmail.com wrote:
On Oct 11, 2012, at 11:04 PM, Pavel Krivanek wrote:
Unfortunately it is not only about a layer between Morphic and Spec.
Whole Spec design is greatly conforming to Morphic. Check out Spec
definitions, they
On Fri, Oct 12, 2012 at 10:45 AM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
Pavel
do you know VW spec, it is an array of symbol and spec is the same.
We should change the api at some point.
The point is that you do not code it by hand but that tools generate them.
Now we are not to
One of the goal of Spec is to be portable.
But sadly, I am not an engineer working full time of Spec.
Right now I have priorities which slow down Spec improvements.
But the infrastructure for having Spec portable is not so far
Ben
On Oct 12, 2012, at 11:28 PM, Pavel Krivanek wrote:
On
Pavel, since i am potential user of Spec, i would like to know more details.
I know it takes more time to explain what exactly you don't like and
propose better alternative,
instead of just generic i don't like it.
OmniBrowser is older than Spec, so it is not a big surprise that it
has more
Unfortunately it is not only about a layer between Morphic and Spec.
Whole Spec design is greatly conforming to Morphic. Check out Spec
definitions, they look almost like transcription of Morphic calls
MethodToolbar class defaultSpec
spec
^ { #Panel.
On Oct 11, 2012, at 11:04 PM, Pavel Krivanek wrote:
Unfortunately it is not only about a layer between Morphic and Spec.
Whole Spec design is greatly conforming to Morphic. Check out Spec
definitions, they look almost like transcription of Morphic calls
MethodToolbar class defaultSpec
On 11 October 2012 23:04, Pavel Krivanek pavel.kriva...@gmail.com wrote:
Unfortunately it is not only about a layer between Morphic and Spec.
Whole Spec design is greatly conforming to Morphic. Check out Spec
definitions, they look almost like transcription of Morphic calls
MethodToolbar
15 matches
Mail list logo
