[SRF] http://raphaeljs.com/

[Dan Bolser-3]

Just to bring this to your attention in the context of SRF (i.e. for
the possibility of a tie in):

http://raphaeljs.com/


P.S. Has anyone experimented with hooking SRFs into the selection section of SD?

For example, it could be interesting to allow click-able bar-charts
instead of 'tag cloud' style listing of filter results.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Yaron Koren]

That is awesome. Certainly there's room for a nicer, more interactive chart
solution than the current Google Chart one (and one that doesn't require
sending your data to an outside service). I think the only other real
possibility for a chart library is Open Flash Chart:

http://teethgrinder.co.uk/open-flash-chart-2/

<http://teethgrinder.co.uk/open-flash-chart-2/>Someone at Vulcan, I believe,
is working on creating an SRF format for Open Flash Chart... though Raphael
(sorry, "Raphaël") does seem more comprehensive; and the fact that's it's
Javascript-based, as opposed to Flash-based, may be an advantage. But of
course, there's nothing wrong with having formats for both. Anyone up for
creating a "raphael" format?

For your second question - having a bar (or pie) chart for selecting filter
values is an interesting idea; I've never seen anything like that, but I
can't think of any reason why it wouldn't work. Once one or the other of
these libraries is in SRF, it would probably make the job a lot easier;
Google Chart charts aren't clickable.

-Yaron


On Wed, Nov 4, 2009 at 6:15 AM, Dan Bolser <dan.bolser@...> wrote:

> Just to bring this to your attention in the context of SRF (i.e. for
> the possibility of a tie in):
>
> http://raphaeljs.com/
>
>
> P.S. Has anyone experimented with hooking SRFs into the selection section
> of SD?
>
> For example, it could be interesting to allow click-able bar-charts
> instead of 'tag cloud' style listing of filter results.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Joel Natividad]

Awesome indeed!

FYI, the "quarantined" Ploticus format does have clickable imagemap
support and does SVG and flash as well (assuming you have the right
Ploticus build).

Hopefully, it will be fixed soon as I know Vulcan is also working on
renovating SRF-Ploticus.  Hopefully, we'll get it fixed faster during
SMW Camp.

Best,
Joel

=======================================================
joel@... * wireless@...
Think Different! (http://en.wikipedia.org/wiki/Think_different#Text)
Imagine Different! (http://www.youtube.com/watch?v=H5tOgRD4EqY)



On Wed, Nov 4, 2009 at 10:41 AM, Yaron Koren <yaron57@...> wrote:

> That is awesome. Certainly there's room for a nicer, more interactive chart
> solution than the current Google Chart one (and one that doesn't require
> sending your data to an outside service). I think the only other real
> possibility for a chart library is Open Flash Chart:
>
> http://teethgrinder.co.uk/open-flash-chart-2/
>
> <http://teethgrinder.co.uk/open-flash-chart-2/>Someone at Vulcan, I believe,
> is working on creating an SRF format for Open Flash Chart... though Raphael
> (sorry, "Raphaël") does seem more comprehensive; and the fact that's it's
> Javascript-based, as opposed to Flash-based, may be an advantage. But of
> course, there's nothing wrong with having formats for both. Anyone up for
> creating a "raphael" format?
>
> For your second question - having a bar (or pie) chart for selecting filter
> values is an interesting idea; I've never seen anything like that, but I
> can't think of any reason why it wouldn't work. Once one or the other of
> these libraries is in SRF, it would probably make the job a lot easier;
> Google Chart charts aren't clickable.
>
> -Yaron
>
>
> On Wed, Nov 4, 2009 at 6:15 AM, Dan Bolser <dan.bolser@...> wrote:
>
>> Just to bring this to your attention in the context of SRF (i.e. for
>> the possibility of a tie in):
>>
>> http://raphaeljs.com/
>>
>>
>> P.S. Has anyone experimented with hooking SRFs into the selection section
>> of SD?
>>
>> For example, it could be interesting to allow click-able bar-charts
>> instead of 'tag cloud' style listing of filter results.
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Semediawiki-user mailing list
>> Semediawiki-user@...
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the following defined:

A string property called RAG. I have 3 values defined for it:
[[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]

In my template definition I have:
! RAG
| [[RAG::{{{RedAmberGreen|}}}]]
|-

In my form definition I have:
! RAG:
| {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
|-

Now, when I'm in the form to create a page, there is no drop-down for
the RAG field. I just get a string field. When I save the default is
correctly saved. However it is displayed in the template as:
[[RAG::Image:Red.png <http://localhost/agility/index.php/File:Red.png>]]
instead of just the red box image.

So why no drop down list and why the [[RAG:: ]] around the image?

This used to work. In an older wiki I've built I have exactly the same
definitions and it works. I get a drop down list of the image strings
and the selected image is displayed
correctly in the template.

Any ideas?

Thanks!
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

Just to clarify

[[RAG::Image:Red.png <http://localhost/agility/index.php/File:Red.png>]]

Shows as

[[RAG::Actual little red box image]] if you get what I mean.

:)

Neill Mitchell wrote:

> I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the following defined:
>
> A string property called RAG. I have 3 values defined for it:
> [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>
> In my template definition I have:
> ! RAG
> | [[RAG::{{{RedAmberGreen|}}}]]
> |-
>
> In my form definition I have:
> ! RAG:
> | {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
> |-
>
> Now, when I'm in the form to create a page, there is no drop-down for
> the RAG field. I just get a string field. When I save the default is
> correctly saved. However it is displayed in the template as:
> [[RAG::Image:Red.png <http://localhost/agility/index.php/File:Red.png>]]
> instead of just the red box image.
>
> So why no drop down list and why the [[RAG:: ]] around the image?
>
> This used to work. In an older wiki I've built I have exactly the same
> definitions and it works. I get a drop down list of the image strings
> and the selected image is displayed
> correctly in the template.
>
> Any ideas?
>
> Thanks!
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>  

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

Hi,

Wikinvest (a wiki about finance and stock data, powered by MW) provides
also some nice interactive charts.
Take e.g. a look at:
http://www.wikinvest.com/stock/Southwest_Airlines_Company_%28LUV%29

Maybe one could find out which chart-library they use?

Regards,
Philipp

Joel Natividad schrieb:

> Awesome indeed!
>
> FYI, the "quarantined" Ploticus format does have clickable imagemap
> support and does SVG and flash as well (assuming you have the right
> Ploticus build).
>
> Hopefully, it will be fixed soon as I know Vulcan is also working on
> renovating SRF-Ploticus.  Hopefully, we'll get it fixed faster during
> SMW Camp.
>
> Best,
> Joel
>
> =======================================================
> joel@... * wireless@...
> Think Different! (http://en.wikipedia.org/wiki/Think_different#Text)
> Imagine Different! (http://www.youtube.com/watch?v=H5tOgRD4EqY)
>
>
>
> On Wed, Nov 4, 2009 at 10:41 AM, Yaron Koren <yaron57@...> wrote:
>  
>> That is awesome. Certainly there's room for a nicer, more interactive chart
>> solution than the current Google Chart one (and one that doesn't require
>> sending your data to an outside service). I think the only other real
>> possibility for a chart library is Open Flash Chart:
>>
>> http://teethgrinder.co.uk/open-flash-chart-2/
>>
>> <http://teethgrinder.co.uk/open-flash-chart-2/>Someone at Vulcan, I believe,
>> is working on creating an SRF format for Open Flash Chart... though Raphael
>> (sorry, "Raphaël") does seem more comprehensive; and the fact that's it's
>> Javascript-based, as opposed to Flash-based, may be an advantage. But of
>> course, there's nothing wrong with having formats for both. Anyone up for
>> creating a "raphael" format?
>>
>> For your second question - having a bar (or pie) chart for selecting filter
>> values is an interesting idea; I've never seen anything like that, but I
>> can't think of any reason why it wouldn't work. Once one or the other of
>> these libraries is in SRF, it would probably make the job a lot easier;
>> Google Chart charts aren't clickable.
>>
>> -Yaron
>>
>>
>> On Wed, Nov 4, 2009 at 6:15 AM, Dan Bolser <dan.bolser@...> wrote:
>>
>>    
>>> Just to bring this to your attention in the context of SRF (i.e. for
>>> the possibility of a tie in):
>>>
>>> http://raphaeljs.com/
>>>
>>>
>>> P.S. Has anyone experimented with hooking SRFs into the selection section
>>> of SD?
>>>
>>> For example, it could be interesting to allow click-able bar-charts
>>> instead of 'tag cloud' style listing of filter results.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>>> trial. Simplify your report design, integration and deployment - and focus
>>> on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> _______________________________________________
>>> Semediawiki-user mailing list
>>> Semediawiki-user@...
>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>>
>>>      
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Semediawiki-user mailing list
>> Semediawiki-user@...
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>
>>    
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>  

--
Professional Services
ontoprise GmbH – know how to use Know-how
- - -
ontoprise has become a Microsoft Certified Partner:
http://www.ontoprise.de/en/home/news/news-en/microsoft-certified-partner/
- - -
An der RaumFabrik 29; 76227 Karlsruhe; Germany
Tel.: [phone]; Fax: [phone]
mailto:zaltenbach@..., www: http://www.ontoprise.de
Registered Office: Karlsruhe, Germany, HRB 109540
Managing Directors: Prof. Dr. Juergen Angele, Hans-Peter Schnurr
- - -


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Yaron Koren]

I think the issue is that the brackets in the property value are messing up
the property call somehow. Whether or not this is a fixable bug, it looks
like there's an easy workaround, which is to make the values for the
property just "Red", "Amber" and "Green" instead, and have the template add
on the image tag and the rest when it's displayed.

-Yaron


On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell <neill@...>wrote:

> Just to clarify
>
> [[RAG::Image:Red.png <http://localhost/agility/index.php/File:Red.png>]]
>
> Shows as
>
> [[RAG::Actual little red box image]] if you get what I mean.
>
> :)
>
> Neill Mitchell wrote:
> > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the following defined:
> >
> > A string property called RAG. I have 3 values defined for it:
> > [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
> >
> > In my template definition I have:
> > ! RAG
> > | [[RAG::{{{RedAmberGreen|}}}]]
> > |-
> >
> > In my form definition I have:
> > ! RAG:
> > | {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
> > |-
> >
> > Now, when I'm in the form to create a page, there is no drop-down for
> > the RAG field. I just get a string field. When I save the default is
> > correctly saved. However it is displayed in the template as:
> > [[RAG::Image:Red.png <http://localhost/agility/index.php/File:Red.png>]]
> > instead of just the red box image.
> >
> > So why no drop down list and why the [[RAG:: ]] around the image?
> >
> > This used to work. In an older wiki I've built I have exactly the same
> > definitions and it works. I get a drop down list of the image strings
> > and the selected image is displayed
> > correctly in the template.
> >
> > Any ideas?
> >
> > Thanks!
> >
> ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day
> > trial. Simplify your report design, integration and deployment - and
> focus on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > Semediawiki-user mailing list
> > Semediawiki-user@...
> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

Hi Yaron.

Thanks for getting back to me.

Unfortunately while this is fine for mandatory fields, I also have other
non mandatory string fields that hold links. So if I put the tagging
into the template then it will always show even when the string is empty.

The version of SF where this is working okay is 1.7.8. Not sure if that
is any help!

Best regards
Neill.
Yaron Koren wrote:

> I think the issue is that the brackets in the property value are
> messing up the property call somehow. Whether or not this is a fixable
> bug, it looks like there's an easy workaround, which is to make the
> values for the property just "Red", "Amber" and "Green" instead, and
> have the template add on the image tag and the rest when it's displayed.
>
> -Yaron
>
>
> On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell <neill@...
> <mailto:neill@...>> wrote:
>
>     Just to clarify
>
>     [[RAG::Image:Red.png
>     <http://localhost/agility/index.php/File:Red.png>]]
>
>     Shows as
>
>     [[RAG::Actual little red box image]] if you get what I mean.
>
>     :)
>
>     Neill Mitchell wrote:
>     > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the following
>     defined:
>     >
>     > A string property called RAG. I have 3 values defined for it:
>     > [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>     >
>     > In my template definition I have:
>     > ! RAG
>     > | [[RAG::{{{RedAmberGreen|}}}]]
>     > |-
>     >
>     > In my form definition I have:
>     > ! RAG:
>     > | {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>     > |-
>     >
>     > Now, when I'm in the form to create a page, there is no
>     drop-down for
>     > the RAG field. I just get a string field. When I save the default is
>     > correctly saved. However it is displayed in the template as:
>     > [[RAG::Image:Red.png
>     <http://localhost/agility/index.php/File:Red.png>]]
>     > instead of just the red box image.
>     >
>     > So why no drop down list and why the [[RAG:: ]] around the image?
>     >
>     > This used to work. In an older wiki I've built I have exactly
>     the same
>     > definitions and it works. I get a drop down list of the image
>     strings
>     > and the selected image is displayed
>     > correctly in the template.
>     >
>     > Any ideas?
>     >
>     > Thanks!
>     >
>     ------------------------------------------------------------------------------
>     > Let Crystal Reports handle the reporting - Free Crystal Reports
>     2008 30-Day
>     > trial. Simplify your report design, integration and deployment -
>     and focus on
>     > what you do best, core application coding. Discover what's new with
>     > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>     > _______________________________________________
>     > Semediawiki-user mailing list
>     > Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     > https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>     >
>     >
>
>
>     ------------------------------------------------------------------------------
>     Let Crystal Reports handle the reporting - Free Crystal Reports
>     2008 30-Day
>     trial. Simplify your report design, integration and deployment -
>     and focus on
>     what you do best, core application coding. Discover what's new with
>     Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>     _______________________________________________
>     Semediawiki-user mailing list
>     Semediawiki-user@...
>     <mailto:Semediawiki-user@...>
>     https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Yaron Koren]

Sorry, is the problem what appears on the page itself? If so, it's not a
Semantic Forms problem... if you're just talking about not being able to
point a property to an image, that's been an issue in SMW for a long time;
the key is to have a line like:

[[Property::Image:ImageName| ]] [[Image:ImageName]]

...in other words, have separate calls for the property and for the image
display.
-Yaron
On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell <neill@...>wrote:

> Hi Yaron.
>
> Thanks for getting back to me.
>
> Unfortunately while this is fine for mandatory fields, I also have other
> non mandatory string fields that hold links. So if I put the tagging into
> the template then it will always show even when the string is empty.
>
> The version of SF where this is working okay is 1.7.8. Not sure if that is
> any help!
>
> Best regards
> Neill.
> Yaron Koren wrote:
>
>> I think the issue is that the brackets in the property value are messing
>> up the property call somehow. Whether or not this is a fixable bug, it looks
>> like there's an easy workaround, which is to make the values for the
>> property just "Red", "Amber" and "Green" instead, and have the template add
>> on the image tag and the rest when it's displayed.
>>
>> -Yaron
>>
>>
>>  On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell <neill@...<mailto:
>> neill@...>> wrote:
>>
>>    Just to clarify
>>
>>    [[RAG::Image:Red.png
>>    <http://localhost/agility/index.php/File:Red.png>]]
>>
>>    Shows as
>>
>>    [[RAG::Actual little red box image]] if you get what I mean.
>>
>>    :)
>>
>>    Neill Mitchell wrote:
>>    > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the following
>>    defined:
>>    >
>>    > A string property called RAG. I have 3 values defined for it:
>>    > [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>>    >
>>    > In my template definition I have:
>>    > ! RAG
>>    > | [[RAG::{{{RedAmberGreen|}}}]]
>>    > |-
>>    >
>>    > In my form definition I have:
>>    > ! RAG:
>>    > | {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>>    > |-
>>    >
>>    > Now, when I'm in the form to create a page, there is no
>>    drop-down for
>>    > the RAG field. I just get a string field. When I save the default is
>>    > correctly saved. However it is displayed in the template as:
>>    > [[RAG::Image:Red.png
>>    <http://localhost/agility/index.php/File:Red.png>]]
>>    > instead of just the red box image.
>>    >
>>    > So why no drop down list and why the [[RAG:: ]] around the image?
>>    >
>>    > This used to work. In an older wiki I've built I have exactly
>>    the same
>>    > definitions and it works. I get a drop down list of the image
>>    strings
>>    > and the selected image is displayed
>>    > correctly in the template.
>>    >
>>    > Any ideas?
>>    >
>>    > Thanks!
>>    >
>>
>>  ------------------------------------------------------------------------------
>>    > Let Crystal Reports handle the reporting - Free Crystal Reports
>>    2008 30-Day
>>    > trial. Simplify your report design, integration and deployment -
>>    and focus on
>>    > what you do best, core application coding. Discover what's new with
>>    > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>    > _______________________________________________
>>    > Semediawiki-user mailing list
>>    > Semediawiki-user@...
>>    <mailto:Semediawiki-user@...>
>>
>>    > https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>    >
>>    >
>>
>>
>>
>>  ------------------------------------------------------------------------------
>>    Let Crystal Reports handle the reporting - Free Crystal Reports
>>    2008 30-Day
>>    trial. Simplify your report design, integration and deployment -
>>    and focus on
>>    what you do best, core application coding. Discover what's new with
>>    Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>    _______________________________________________
>>    Semediawiki-user mailing list
>>    Semediawiki-user@...
>>    <mailto:Semediawiki-user@...>
>>
>>    https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>
>>
>>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

Hi Yaron.

No, what I am saying is that if I move the [[image:]] to the template to
get round the property/form string problem then the user will see
[[image:]] if the property string is empty. This isn't just images
either. Normal links have the same problem.

If I have a string property "Link", for example and the following:

Form def:
! Article Link:
| {{{field|ArticleLink|}}}
|-

Template def:
! Article Link
| [[Link::{{{ArticleLink|}}}]]
|}

Then when the user puts in, say, [[MyPage]], what you see on the page is
[[Link::MyPage]]

If I were to move the [[]] to the template to solve this problem as you
originally suggested, you will see [[]] displayed if no Link string was
entered (quite legitimately) in the form. This obviously looks wrong.

You see my problem?  This used to all work fine.

Cheers
Neill.
Yaron Koren wrote:

> Sorry, is the problem what appears on the page itself? If so, it's not
> a Semantic Forms problem... if you're just talking about not being
> able to point a property to an image, that's been an issue in SMW for
> a long time; the key is to have a line like:
>  
> [[Property::Image:ImageName| ]] [[Image:ImageName]]
>  
> ...in other words, have separate calls for the property and for the
> image display.
> -Yaron
> On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell <neill@...
> <mailto:neill@...>> wrote:
>
>     Hi Yaron.
>
>     Thanks for getting back to me.
>
>     Unfortunately while this is fine for mandatory fields, I also have
>     other non mandatory string fields that hold links. So if I put the
>     tagging into the template then it will always show even when the
>     string is empty.
>
>     The version of SF where this is working okay is 1.7.8. Not sure if
>     that is any help!
>
>     Best regards
>     Neill.
>     Yaron Koren wrote:
>
>         I think the issue is that the brackets in the property value
>         are messing up the property call somehow. Whether or not this
>         is a fixable bug, it looks like there's an easy workaround,
>         which is to make the values for the property just "Red",
>         "Amber" and "Green" instead, and have the template add on the
>         image tag and the rest when it's displayed.
>
>         -Yaron
>
>
>         On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell
>         <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>>
>         wrote:
>
>            Just to clarify
>
>            [[RAG::Image:Red.png
>            <http://localhost/agility/index.php/File:Red.png>]]
>
>            Shows as
>
>            [[RAG::Actual little red box image]] if you get what I mean.
>
>            :)
>
>            Neill Mitchell wrote:
>            > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the
>         following
>            defined:
>            >
>            > A string property called RAG. I have 3 values defined for it:
>            > [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>            >
>            > In my template definition I have:
>            > ! RAG
>            > | [[RAG::{{{RedAmberGreen|}}}]]
>            > |-
>            >
>            > In my form definition I have:
>            > ! RAG:
>            > |
>         {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>            > |-
>            >
>            > Now, when I'm in the form to create a page, there is no
>            drop-down for
>            > the RAG field. I just get a string field. When I save the
>         default is
>            > correctly saved. However it is displayed in the template as:
>            > [[RAG::Image:Red.png
>            <http://localhost/agility/index.php/File:Red.png>]]
>            > instead of just the red box image.
>            >
>            > So why no drop down list and why the [[RAG:: ]] around
>         the image?
>            >
>            > This used to work. In an older wiki I've built I have exactly
>            the same
>            > definitions and it works. I get a drop down list of the image
>            strings
>            > and the selected image is displayed
>            > correctly in the template.
>            >
>            > Any ideas?
>            >
>            > Thanks!
>            >
>          
>          ------------------------------------------------------------------------------
>            > Let Crystal Reports handle the reporting - Free Crystal
>         Reports
>            2008 30-Day
>            > trial. Simplify your report design, integration and
>         deployment -
>            and focus on
>            > what you do best, core application coding. Discover
>         what's new with
>            > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>            > _______________________________________________
>            > Semediawiki-user mailing list
>            > Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>            <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>
>            > https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>            >
>            >
>
>
>          
>          ------------------------------------------------------------------------------
>            Let Crystal Reports handle the reporting - Free Crystal Reports
>            2008 30-Day
>            trial. Simplify your report design, integration and
>         deployment -
>            and focus on
>            what you do best, core application coding. Discover what's
>         new with
>            Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>            _______________________________________________
>            Semediawiki-user mailing list
>            Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>            <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>
>            https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Yaron Koren]

I see. Well, that doesn't sound like a Semantic Forms issue, and it's
probably not a Semantic MediaWiki issue either... it sounds like MediaWiki's
own handling changed at some point. You may have to use the #if function to
solve it.

-Yaron

On Thu, Nov 5, 2009 at 10:00 AM, Neill Mitchell <neill@...>wrote:

> Hi Yaron.
>
> No, what I am saying is that if I move the [[image:]] to the template to
> get round the property/form string problem then the user will see [[image:]]
> if the property string is empty. This isn't just images either. Normal links
> have the same problem.
>
> If I have a string property "Link", for example and the following:
>
> Form def:
> ! Article Link:
> | {{{field|ArticleLink|}}}
> |-
>
> Template def:
> ! Article Link
> | [[Link::{{{ArticleLink|}}}]]
> |}
>
> Then when the user puts in, say, [[MyPage]], what you see on the page is
> [[Link::MyPage]]
>
> If I were to move the [[]] to the template to solve this problem as you
> originally suggested, you will see [[]] displayed if no Link string was
> entered (quite legitimately) in the form. This obviously looks wrong.
>
> You see my problem?  This used to all work fine.
>
> Cheers
> Neill.
> Yaron Koren wrote:
>
>> Sorry, is the problem what appears on the page itself? If so, it's not a
>> Semantic Forms problem... if you're just talking about not being able to
>> point a property to an image, that's been an issue in SMW for a long time;
>> the key is to have a line like:
>>  [[Property::Image:ImageName| ]] [[Image:ImageName]]
>>  ...in other words, have separate calls for the property and for the image
>> display.
>> -Yaron
>> On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell <neill@...<mailto:
>> neill@...>> wrote:
>>
>>    Hi Yaron.
>>
>>    Thanks for getting back to me.
>>
>>    Unfortunately while this is fine for mandatory fields, I also have
>>    other non mandatory string fields that hold links. So if I put the
>>    tagging into the template then it will always show even when the
>>    string is empty.
>>
>>    The version of SF where this is working okay is 1.7.8. Not sure if
>>    that is any help!
>>
>>    Best regards
>>    Neill.
>>    Yaron Koren wrote:
>>
>>        I think the issue is that the brackets in the property value
>>        are messing up the property call somehow. Whether or not this
>>        is a fixable bug, it looks like there's an easy workaround,
>>        which is to make the values for the property just "Red",
>>        "Amber" and "Green" instead, and have the template add on the
>>        image tag and the rest when it's displayed.
>>
>>        -Yaron
>>
>>
>>        On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell
>>        <neill@... <mailto:neill@...>
>>        <mailto:neill@... <mailto:neill@...>>>
>>
>>        wrote:
>>
>>           Just to clarify
>>
>>           [[RAG::Image:Red.png
>>           <http://localhost/agility/index.php/File:Red.png>]]
>>
>>           Shows as
>>
>>           [[RAG::Actual little red box image]] if you get what I mean.
>>
>>           :)
>>
>>           Neill Mitchell wrote:
>>           > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the
>>        following
>>           defined:
>>           >
>>           > A string property called RAG. I have 3 values defined for it:
>>           > [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>>           >
>>           > In my template definition I have:
>>           > ! RAG
>>           > | [[RAG::{{{RedAmberGreen|}}}]]
>>           > |-
>>           >
>>           > In my form definition I have:
>>           > ! RAG:
>>           > |
>>        {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>>           > |-
>>           >
>>           > Now, when I'm in the form to create a page, there is no
>>           drop-down for
>>           > the RAG field. I just get a string field. When I save the
>>        default is
>>           > correctly saved. However it is displayed in the template as:
>>           > [[RAG::Image:Red.png
>>           <http://localhost/agility/index.php/File:Red.png>]]
>>           > instead of just the red box image.
>>           >
>>           > So why no drop down list and why the [[RAG:: ]] around
>>        the image?
>>           >
>>           > This used to work. In an older wiki I've built I have exactly
>>           the same
>>           > definitions and it works. I get a drop down list of the image
>>           strings
>>           > and the selected image is displayed
>>           > correctly in the template.
>>           >
>>           > Any ideas?
>>           >
>>           > Thanks!
>>           >
>>
>> ------------------------------------------------------------------------------
>>           > Let Crystal Reports handle the reporting - Free Crystal
>>        Reports
>>           2008 30-Day
>>           > trial. Simplify your report design, integration and
>>        deployment -
>>           and focus on
>>           > what you do best, core application coding. Discover
>>        what's new with
>>           > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>           > _______________________________________________
>>           > Semediawiki-user mailing list
>>           > Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>           <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>
>>           > https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>           >
>>           >
>>
>>
>>
>> ------------------------------------------------------------------------------
>>           Let Crystal Reports handle the reporting - Free Crystal Reports
>>           2008 30-Day
>>           trial. Simplify your report design, integration and
>>        deployment -
>>           and focus on
>>           what you do best, core application coding. Discover what's
>>        new with
>>           Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>           _______________________________________________
>>           Semediawiki-user mailing list
>>           Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>           <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>
>>           https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>
>>
>>
>>
>>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

Hi Yaron.

But why can I no longer have
[[Image:Red]],[[Image:Amber]],[[Image:Green]] in the property? Or any []
characters in fact. You should be able to have any characters in a
string property. I know there are others you can't have either, :: for
example. It completely trashes the page. Which is a real pain if you are
running a SMW for a C++ development group! ;) I have to tell my users to
put a space between the colons.

I think we are getting confused here. You suggested a work around to the
issue of not being able to have [] characters in the property as it
causes a parsing error with SF. You suggested moving the [] chars from
the property definition to the template to get round the problem. I'm
simply saying that your suggested work around will display  []
characters if the string is empty.

Am I making sense?

Cheers
Neill.



Yaron Koren wrote:

> I see. Well, that doesn't sound like a Semantic Forms issue, and it's
> probably not a Semantic MediaWiki issue either... it sounds like
> MediaWiki's own handling changed at some point. You may have to use
> the #if function to solve it.
>  
> -Yaron
>
> On Thu, Nov 5, 2009 at 10:00 AM, Neill Mitchell <neill@...
> <mailto:neill@...>> wrote:
>
>     Hi Yaron.
>
>     No, what I am saying is that if I move the [[image:]] to the
>     template to get round the property/form string problem then the
>     user will see [[image:]] if the property string is empty. This
>     isn't just images either. Normal links have the same problem.
>
>     If I have a string property "Link", for example and the following:
>
>     Form def:
>     ! Article Link:
>     | {{{field|ArticleLink|}}}
>     |-
>
>     Template def:
>     ! Article Link
>     | [[Link::{{{ArticleLink|}}}]]
>     |}
>
>     Then when the user puts in, say, [[MyPage]], what you see on the
>     page is [[Link::MyPage]]
>
>     If I were to move the [[]] to the template to solve this problem
>     as you originally suggested, you will see [[]] displayed if no
>     Link string was entered (quite legitimately) in the form. This
>     obviously looks wrong.
>
>     You see my problem?  This used to all work fine.
>
>     Cheers
>     Neill.
>     Yaron Koren wrote:
>
>         Sorry, is the problem what appears on the page itself? If so,
>         it's not a Semantic Forms problem... if you're just talking
>         about not being able to point a property to an image, that's
>         been an issue in SMW for a long time; the key is to have a
>         line like:
>          [[Property::Image:ImageName| ]] [[Image:ImageName]]
>          ...in other words, have separate calls for the property and
>         for the image display.
>         -Yaron
>         On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell
>         <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>>
>         wrote:
>
>            Hi Yaron.
>
>            Thanks for getting back to me.
>
>            Unfortunately while this is fine for mandatory fields, I
>         also have
>            other non mandatory string fields that hold links. So if I
>         put the
>            tagging into the template then it will always show even
>         when the
>            string is empty.
>
>            The version of SF where this is working okay is 1.7.8. Not
>         sure if
>            that is any help!
>
>            Best regards
>            Neill.
>            Yaron Koren wrote:
>
>                I think the issue is that the brackets in the property
>         value
>                are messing up the property call somehow. Whether or
>         not this
>                is a fixable bug, it looks like there's an easy workaround,
>                which is to make the values for the property just "Red",
>                "Amber" and "Green" instead, and have the template add
>         on the
>                image tag and the rest when it's displayed.
>
>                -Yaron
>
>
>                On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell
>                <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>
>                <mailto:neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>>>
>
>                wrote:
>
>                   Just to clarify
>
>                   [[RAG::Image:Red.png
>                   <http://localhost/agility/index.php/File:Red.png>]]
>
>                   Shows as
>
>                   [[RAG::Actual little red box image]] if you get what
>         I mean.
>
>                   :)
>
>                   Neill Mitchell wrote:
>                   > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the
>                following
>                   defined:
>                   >
>                   > A string property called RAG. I have 3 values
>         defined for it:
>                   >
>         [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>                   >
>                   > In my template definition I have:
>                   > ! RAG
>                   > | [[RAG::{{{RedAmberGreen|}}}]]
>                   > |-
>                   >
>                   > In my form definition I have:
>                   > ! RAG:
>                   > |
>              
>          {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>                   > |-
>                   >
>                   > Now, when I'm in the form to create a page, there
>         is no
>                   drop-down for
>                   > the RAG field. I just get a string field. When I
>         save the
>                default is
>                   > correctly saved. However it is displayed in the
>         template as:
>                   > [[RAG::Image:Red.png
>                   <http://localhost/agility/index.php/File:Red.png>]]
>                   > instead of just the red box image.
>                   >
>                   > So why no drop down list and why the [[RAG:: ]] around
>                the image?
>                   >
>                   > This used to work. In an older wiki I've built I
>         have exactly
>                   the same
>                   > definitions and it works. I get a drop down list
>         of the image
>                   strings
>                   > and the selected image is displayed
>                   > correctly in the template.
>                   >
>                   > Any ideas?
>                   >
>                   > Thanks!
>                   >
>                        
>         ------------------------------------------------------------------------------
>                   > Let Crystal Reports handle the reporting - Free
>         Crystal
>                Reports
>                   2008 30-Day
>                   > trial. Simplify your report design, integration and
>                deployment -
>                   and focus on
>                   > what you do best, core application coding. Discover
>                what's new with
>                   > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>                   > _______________________________________________
>                   > Semediawiki-user mailing list
>                   > Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                   <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>
>                   >
>         https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>                   >
>                   >
>
>
>                        
>         ------------------------------------------------------------------------------
>                   Let Crystal Reports handle the reporting - Free
>         Crystal Reports
>                   2008 30-Day
>                   trial. Simplify your report design, integration and
>                deployment -
>                   and focus on
>                   what you do best, core application coding. Discover
>         what's
>                new with
>                   Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>                   _______________________________________________
>                   Semediawiki-user mailing list
>                   Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                   <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>
>                  
>         https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>
>
>
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Yaron Koren]

Okay, I confess I don't quite understand the issue, but that may be because
you're experiencing two or three problems at the same time... adding this to
LocalSettings.php may help, though:

$smwgLinksInValues = true;

-Yaron


On Thu, Nov 5, 2009 at 10:25 AM, Neill Mitchell <neill@...>wrote:

> Hi Yaron.
>
> But why can I no longer have [[Image:Red]],[[Image:Amber]],[[Image:Green]]
> in the property? Or any [] characters in fact. You should be able to have
> any characters in a string property. I know there are others you can't have
> either, :: for example. It completely trashes the page. Which is a real pain
> if you are running a SMW for a C++ development group! ;) I have to tell my
> users to put a space between the colons.
>
> I think we are getting confused here. You suggested a work around to the
> issue of not being able to have [] characters in the property as it causes a
> parsing error with SF. You suggested moving the [] chars from the property
> definition to the template to get round the problem. I'm simply saying that
> your suggested work around will display  [] characters if the string is
> empty.
>
> Am I making sense?
>
>
> Cheers
> Neill.
>
>
>
> Yaron Koren wrote:
>
>> I see. Well, that doesn't sound like a Semantic Forms issue, and it's
>> probably not a Semantic MediaWiki issue either... it sounds like MediaWiki's
>> own handling changed at some point. You may have to use the #if function to
>> solve it.
>>  -Yaron
>>
>>  On Thu, Nov 5, 2009 at 10:00 AM, Neill Mitchell <neill@...<mailto:
>> neill@...>> wrote:
>>
>>    Hi Yaron.
>>
>>    No, what I am saying is that if I move the [[image:]] to the
>>    template to get round the property/form string problem then the
>>    user will see [[image:]] if the property string is empty. This
>>    isn't just images either. Normal links have the same problem.
>>
>>    If I have a string property "Link", for example and the following:
>>
>>    Form def:
>>    ! Article Link:
>>    | {{{field|ArticleLink|}}}
>>    |-
>>
>>    Template def:
>>    ! Article Link
>>    | [[Link::{{{ArticleLink|}}}]]
>>    |}
>>
>>    Then when the user puts in, say, [[MyPage]], what you see on the
>>    page is [[Link::MyPage]]
>>
>>    If I were to move the [[]] to the template to solve this problem
>>    as you originally suggested, you will see [[]] displayed if no
>>    Link string was entered (quite legitimately) in the form. This
>>    obviously looks wrong.
>>
>>    You see my problem?  This used to all work fine.
>>
>>    Cheers
>>    Neill.
>>    Yaron Koren wrote:
>>
>>        Sorry, is the problem what appears on the page itself? If so,
>>        it's not a Semantic Forms problem... if you're just talking
>>        about not being able to point a property to an image, that's
>>        been an issue in SMW for a long time; the key is to have a
>>        line like:
>>         [[Property::Image:ImageName| ]] [[Image:ImageName]]
>>         ...in other words, have separate calls for the property and
>>        for the image display.
>>        -Yaron
>>        On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell
>>        <neill@... <mailto:neill@...>
>>         <mailto:neill@... <mailto:neill@...>>>
>>        wrote:
>>
>>           Hi Yaron.
>>
>>           Thanks for getting back to me.
>>
>>           Unfortunately while this is fine for mandatory fields, I
>>        also have
>>           other non mandatory string fields that hold links. So if I
>>        put the
>>           tagging into the template then it will always show even
>>        when the
>>           string is empty.
>>
>>           The version of SF where this is working okay is 1.7.8. Not
>>        sure if
>>           that is any help!
>>
>>           Best regards
>>           Neill.
>>           Yaron Koren wrote:
>>
>>               I think the issue is that the brackets in the property
>>        value
>>               are messing up the property call somehow. Whether or
>>        not this
>>               is a fixable bug, it looks like there's an easy workaround,
>>               which is to make the values for the property just "Red",
>>               "Amber" and "Green" instead, and have the template add
>>        on the
>>               image tag and the rest when it's displayed.
>>
>>               -Yaron
>>
>>
>>               On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell
>>               <neill@... <mailto:neill@...>
>>        <mailto:neill@... <mailto:neill@...>>
>>               <mailto:neill@...
>>        <mailto:neill@...> <mailto:neill@...
>>        <mailto:neill@...>>>>
>>
>>               wrote:
>>
>>                  Just to clarify
>>
>>                  [[RAG::Image:Red.png
>>                  <http://localhost/agility/index.php/File:Red.png>]]
>>
>>                  Shows as
>>
>>                  [[RAG::Actual little red box image]] if you get what
>>        I mean.
>>
>>                  :)
>>
>>                  Neill Mitchell wrote:
>>                  > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3. I have the
>>               following
>>                  defined:
>>                  >
>>                  > A string property called RAG. I have 3 values
>>        defined for it:
>>                  >
>>        [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>>                  >
>>                  > In my template definition I have:
>>                  > ! RAG
>>                  > | [[RAG::{{{RedAmberGreen|}}}]]
>>                  > |-
>>                  >
>>                  > In my form definition I have:
>>                  > ! RAG:
>>                  > |
>>
>> {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>>                  > |-
>>                  >
>>                  > Now, when I'm in the form to create a page, there
>>        is no
>>                  drop-down for
>>                  > the RAG field. I just get a string field. When I
>>        save the
>>               default is
>>                  > correctly saved. However it is displayed in the
>>        template as:
>>                  > [[RAG::Image:Red.png
>>                  <http://localhost/agility/index.php/File:Red.png>]]
>>                  > instead of just the red box image.
>>                  >
>>                  > So why no drop down list and why the [[RAG:: ]] around
>>               the image?
>>                  >
>>                  > This used to work. In an older wiki I've built I
>>        have exactly
>>                  the same
>>                  > definitions and it works. I get a drop down list
>>        of the image
>>                  strings
>>                  > and the selected image is displayed
>>                  > correctly in the template.
>>                  >
>>                  > Any ideas?
>>                  >
>>                  > Thanks!
>>                  >
>>
>>  ------------------------------------------------------------------------------
>>                  > Let Crystal Reports handle the reporting - Free
>>        Crystal
>>               Reports
>>                  2008 30-Day
>>                  > trial. Simplify your report design, integration and
>>               deployment -
>>                  and focus on
>>                  > what you do best, core application coding. Discover
>>               what's new with
>>                  > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>                  > _______________________________________________
>>                  > Semediawiki-user mailing list
>>                  > Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>                  <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>>
>>
>>                  >
>>        https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>                  >
>>                  >
>>
>>
>>
>>  ------------------------------------------------------------------------------
>>                  Let Crystal Reports handle the reporting - Free
>>        Crystal Reports
>>                  2008 30-Day
>>                  trial. Simplify your report design, integration and
>>               deployment -
>>                  and focus on
>>                  what you do best, core application coding. Discover
>>        what's
>>               new with
>>                  Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>                  _______________________________________________
>>                  Semediawiki-user mailing list
>>                  Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>                  <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>>
>>
>>
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>
>>
>>
>>
>>
>>
>>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

Aha! That sorts it out! Man, I have pored over the two LocalSettings.php
files for ages and must've missed it :) One more item to go into my SMW
tips and trips instance so I don't lose it again!

It is always difficult to explain stuff like this. I was going to
suggest that you make the mods to my example to get us to a common
point, but now it's working anyway. Not a bug, which is good news all round.

Now all I have to sort out is this MS Office file upload issue ;)

Thanks a lot for your patience Yaron.

Cheers
Neill.
Yaron Koren wrote:

> Okay, I confess I don't quite understand the issue, but that may be
> because you're experiencing two or three problems at the same time...
> adding this to LocalSettings.php may help, though:
>  
> $smwgLinksInValues = true;
>  
> -Yaron
>
>  
> On Thu, Nov 5, 2009 at 10:25 AM, Neill Mitchell <neill@...
> <mailto:neill@...>> wrote:
>
>     Hi Yaron.
>
>     But why can I no longer have
>     [[Image:Red]],[[Image:Amber]],[[Image:Green]] in the property? Or
>     any [] characters in fact. You should be able to have any
>     characters in a string property. I know there are others you can't
>     have either, :: for example. It completely trashes the page. Which
>     is a real pain if you are running a SMW for a C++ development
>     group! ;) I have to tell my users to put a space between the colons.
>
>     I think we are getting confused here. You suggested a work around
>     to the issue of not being able to have [] characters in the
>     property as it causes a parsing error with SF. You suggested
>     moving the [] chars from the property definition to the template
>     to get round the problem. I'm simply saying that your suggested
>     work around will display  [] characters if the string is empty.
>
>     Am I making sense?
>
>
>     Cheers
>     Neill.
>
>
>
>     Yaron Koren wrote:
>
>         I see. Well, that doesn't sound like a Semantic Forms issue,
>         and it's probably not a Semantic MediaWiki issue either... it
>         sounds like MediaWiki's own handling changed at some point.
>         You may have to use the #if function to solve it.
>          -Yaron
>
>         On Thu, Nov 5, 2009 at 10:00 AM, Neill Mitchell
>         <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>>
>         wrote:
>
>            Hi Yaron.
>
>            No, what I am saying is that if I move the [[image:]] to the
>            template to get round the property/form string problem then the
>            user will see [[image:]] if the property string is empty. This
>            isn't just images either. Normal links have the same problem.
>
>            If I have a string property "Link", for example and the
>         following:
>
>            Form def:
>            ! Article Link:
>            | {{{field|ArticleLink|}}}
>            |-
>
>            Template def:
>            ! Article Link
>            | [[Link::{{{ArticleLink|}}}]]
>            |}
>
>            Then when the user puts in, say, [[MyPage]], what you see
>         on the
>            page is [[Link::MyPage]]
>
>            If I were to move the [[]] to the template to solve this
>         problem
>            as you originally suggested, you will see [[]] displayed if no
>            Link string was entered (quite legitimately) in the form. This
>            obviously looks wrong.
>
>            You see my problem?  This used to all work fine.
>
>            Cheers
>            Neill.
>            Yaron Koren wrote:
>
>                Sorry, is the problem what appears on the page itself?
>         If so,
>                it's not a Semantic Forms problem... if you're just talking
>                about not being able to point a property to an image,
>         that's
>                been an issue in SMW for a long time; the key is to have a
>                line like:
>                 [[Property::Image:ImageName| ]] [[Image:ImageName]]
>                 ...in other words, have separate calls for the
>         property and
>                for the image display.
>                -Yaron
>                On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell
>                <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>
>                <mailto:neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>>>
>                wrote:
>
>                   Hi Yaron.
>
>                   Thanks for getting back to me.
>
>                   Unfortunately while this is fine for mandatory fields, I
>                also have
>                   other non mandatory string fields that hold links.
>         So if I
>                put the
>                   tagging into the template then it will always show even
>                when the
>                   string is empty.
>
>                   The version of SF where this is working okay is
>         1.7.8. Not
>                sure if
>                   that is any help!
>
>                   Best regards
>                   Neill.
>                   Yaron Koren wrote:
>
>                       I think the issue is that the brackets in the
>         property
>                value
>                       are messing up the property call somehow. Whether or
>                not this
>                       is a fixable bug, it looks like there's an easy
>         workaround,
>                       which is to make the values for the property
>         just "Red",
>                       "Amber" and "Green" instead, and have the
>         template add
>                on the
>                       image tag and the rest when it's displayed.
>
>                       -Yaron
>
>
>                       On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell
>                       <neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>
>                <mailto:neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>>
>                       <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>> <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>>>>
>
>                       wrote:
>
>                          Just to clarify
>
>                          [[RAG::Image:Red.png
>                        
>          <http://localhost/agility/index.php/File:Red.png>]]
>
>                          Shows as
>
>                          [[RAG::Actual little red box image]] if you
>         get what
>                I mean.
>
>                          :)
>
>                          Neill Mitchell wrote:
>                          > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3.
>         I have the
>                       following
>                          defined:
>                          >
>                          > A string property called RAG. I have 3 values
>                defined for it:
>                          >
>                [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>                          >
>                          > In my template definition I have:
>                          > ! RAG
>                          > | [[RAG::{{{RedAmberGreen|}}}]]
>                          > |-
>                          >
>                          > In my form definition I have:
>                          > ! RAG:
>                          > |
>                            
>         {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>                          > |-
>                          >
>                          > Now, when I'm in the form to create a page,
>         there
>                is no
>                          drop-down for
>                          > the RAG field. I just get a string field.
>         When I
>                save the
>                       default is
>                          > correctly saved. However it is displayed in the
>                template as:
>                          > [[RAG::Image:Red.png
>                        
>          <http://localhost/agility/index.php/File:Red.png>]]
>                          > instead of just the red box image.
>                          >
>                          > So why no drop down list and why the
>         [[RAG:: ]] around
>                       the image?
>                          >
>                          > This used to work. In an older wiki I've
>         built I
>                have exactly
>                          the same
>                          > definitions and it works. I get a drop down
>         list
>                of the image
>                          strings
>                          > and the selected image is displayed
>                          > correctly in the template.
>                          >
>                          > Any ideas?
>                          >
>                          > Thanks!
>                          >
>                                    
>          ------------------------------------------------------------------------------
>                          > Let Crystal Reports handle the reporting - Free
>                Crystal
>                       Reports
>                          2008 30-Day
>                          > trial. Simplify your report design,
>         integration and
>                       deployment -
>                          and focus on
>                          > what you do best, core application coding.
>         Discover
>                       what's new with
>                          > Crystal Reports now.
>          http://p.sf.net/sfu/bobj-july
>                          > _______________________________________________
>                          > Semediawiki-user mailing list
>                          > Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>                        
>          <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>>
>
>                          >
>              
>          https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>                          >
>                          >
>
>
>                                    
>          ------------------------------------------------------------------------------
>                          Let Crystal Reports handle the reporting - Free
>                Crystal Reports
>                          2008 30-Day
>                          trial. Simplify your report design,
>         integration and
>                       deployment -
>                          and focus on
>                          what you do best, core application coding.
>         Discover
>                what's
>                       new with
>                          Crystal Reports now.
>          http://p.sf.net/sfu/bobj-july
>                          _______________________________________________
>                          Semediawiki-user mailing list
>                          Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>                        
>          <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>>
>
>                              
>          https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>
>
>
>
>
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Yaron Koren]

That's great! Let me take this opportunity to plug the SMW quick reference,
AKA the SMW cheat sheet:

http://semantic-mediawiki.org/wiki/Image:SMW_quick_reference.pdf

$smwgLinksInValues is mentioned right in the first column; in addition to
lots of other good stuff.

-Yaron

On Thu, Nov 5, 2009 at 11:04 AM, Neill Mitchell <neill@...>wrote:

> Aha! That sorts it out! Man, I have pored over the two LocalSettings.php
> files for ages and must've missed it :) One more item to go into my SMW tips
> and trips instance so I don't lose it again!
>
> It is always difficult to explain stuff like this. I was going to suggest
> that you make the mods to my example to get us to a common point, but now
> it's working anyway. Not a bug, which is good news all round.
>
> Now all I have to sort out is this MS Office file upload issue ;)
>
> Thanks a lot for your patience Yaron.
>
>
> Cheers
> Neill.
> Yaron Koren wrote:
>
>> Okay, I confess I don't quite understand the issue, but that may be
>> because you're experiencing two or three problems at the same time... adding
>> this to LocalSettings.php may help, though:
>>  $smwgLinksInValues = true;
>>  -Yaron
>>
>>   On Thu, Nov 5, 2009 at 10:25 AM, Neill Mitchell <neill@...<mailto:
>> neill@...>> wrote:
>>
>>    Hi Yaron.
>>
>>    But why can I no longer have
>>    [[Image:Red]],[[Image:Amber]],[[Image:Green]] in the property? Or
>>    any [] characters in fact. You should be able to have any
>>    characters in a string property. I know there are others you can't
>>    have either, :: for example. It completely trashes the page. Which
>>    is a real pain if you are running a SMW for a C++ development
>>    group! ;) I have to tell my users to put a space between the colons.
>>
>>    I think we are getting confused here. You suggested a work around
>>    to the issue of not being able to have [] characters in the
>>    property as it causes a parsing error with SF. You suggested
>>    moving the [] chars from the property definition to the template
>>    to get round the problem. I'm simply saying that your suggested
>>    work around will display  [] characters if the string is empty.
>>
>>    Am I making sense?
>>
>>
>>    Cheers
>>    Neill.
>>
>>
>>
>>    Yaron Koren wrote:
>>
>>        I see. Well, that doesn't sound like a Semantic Forms issue,
>>        and it's probably not a Semantic MediaWiki issue either... it
>>        sounds like MediaWiki's own handling changed at some point.
>>        You may have to use the #if function to solve it.
>>         -Yaron
>>
>>        On Thu, Nov 5, 2009 at 10:00 AM, Neill Mitchell
>>        <neill@... <mailto:neill@...>
>>         <mailto:neill@... <mailto:neill@...>>>
>>        wrote:
>>
>>           Hi Yaron.
>>
>>           No, what I am saying is that if I move the [[image:]] to the
>>           template to get round the property/form string problem then the
>>           user will see [[image:]] if the property string is empty. This
>>           isn't just images either. Normal links have the same problem.
>>
>>           If I have a string property "Link", for example and the
>>        following:
>>
>>           Form def:
>>           ! Article Link:
>>           | {{{field|ArticleLink|}}}
>>           |-
>>
>>           Template def:
>>           ! Article Link
>>           | [[Link::{{{ArticleLink|}}}]]
>>           |}
>>
>>           Then when the user puts in, say, [[MyPage]], what you see
>>        on the
>>           page is [[Link::MyPage]]
>>
>>           If I were to move the [[]] to the template to solve this
>>        problem
>>           as you originally suggested, you will see [[]] displayed if no
>>           Link string was entered (quite legitimately) in the form. This
>>           obviously looks wrong.
>>
>>           You see my problem?  This used to all work fine.
>>
>>           Cheers
>>           Neill.
>>           Yaron Koren wrote:
>>
>>               Sorry, is the problem what appears on the page itself?
>>        If so,
>>               it's not a Semantic Forms problem... if you're just talking
>>               about not being able to point a property to an image,
>>        that's
>>               been an issue in SMW for a long time; the key is to have a
>>               line like:
>>                [[Property::Image:ImageName| ]] [[Image:ImageName]]
>>                ...in other words, have separate calls for the
>>        property and
>>               for the image display.
>>               -Yaron
>>               On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell
>>               <neill@... <mailto:neill@...>
>>        <mailto:neill@... <mailto:neill@...>>
>>                <mailto:neill@...
>>        <mailto:neill@...> <mailto:neill@...
>>        <mailto:neill@...>>>>
>>               wrote:
>>
>>                  Hi Yaron.
>>
>>                  Thanks for getting back to me.
>>
>>                  Unfortunately while this is fine for mandatory fields, I
>>               also have
>>                  other non mandatory string fields that hold links.
>>        So if I
>>               put the
>>                  tagging into the template then it will always show even
>>               when the
>>                  string is empty.
>>
>>                  The version of SF where this is working okay is
>>        1.7.8. Not
>>               sure if
>>                  that is any help!
>>
>>                  Best regards
>>                  Neill.
>>                  Yaron Koren wrote:
>>
>>                      I think the issue is that the brackets in the
>>        property
>>               value
>>                      are messing up the property call somehow. Whether or
>>               not this
>>                      is a fixable bug, it looks like there's an easy
>>        workaround,
>>                      which is to make the values for the property
>>        just "Red",
>>                      "Amber" and "Green" instead, and have the
>>        template add
>>               on the
>>                      image tag and the rest when it's displayed.
>>
>>                      -Yaron
>>
>>
>>                      On Wed, Nov 4, 2009 at 11:07 AM, Neill Mitchell
>>                      <neill@...
>>        <mailto:neill@...> <mailto:neill@...
>>        <mailto:neill@...>>
>>               <mailto:neill@...
>>        <mailto:neill@...> <mailto:neill@...
>>        <mailto:neill@...>>>
>>                      <mailto:neill@...
>>        <mailto:neill@...>
>>               <mailto:neill@...
>>        <mailto:neill@...>> <mailto:neill@...
>>        <mailto:neill@...>
>>               <mailto:neill@...
>>        <mailto:neill@...>>>>>
>>
>>                      wrote:
>>
>>                         Just to clarify
>>
>>                         [[RAG::Image:Red.png
>>                               <
>> http://localhost/agility/index.php/File:Red.png>]]
>>
>>                         Shows as
>>
>>                         [[RAG::Actual little red box image]] if you
>>        get what
>>               I mean.
>>
>>                         :)
>>
>>                         Neill Mitchell wrote:
>>                         > I've got SMW 1.4.3 MW 1.15.1 and SF 1.8.3.
>>        I have the
>>                      following
>>                         defined:
>>                         >
>>                         > A string property called RAG. I have 3 values
>>               defined for it:
>>                         >
>>               [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>>                         >
>>                         > In my template definition I have:
>>                         > ! RAG
>>                         > | [[RAG::{{{RedAmberGreen|}}}]]
>>                         > |-
>>                         >
>>                         > In my form definition I have:
>>                         > ! RAG:
>>                         > |
>>
>>  {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>>                         > |-
>>                         >
>>                         > Now, when I'm in the form to create a page,
>>        there
>>               is no
>>                         drop-down for
>>                         > the RAG field. I just get a string field.
>>        When I
>>               save the
>>                      default is
>>                         > correctly saved. However it is displayed in the
>>               template as:
>>                         > [[RAG::Image:Red.png
>>                               <
>> http://localhost/agility/index.php/File:Red.png>]]
>>                         > instead of just the red box image.
>>                         >
>>                         > So why no drop down list and why the
>>        [[RAG:: ]] around
>>                      the image?
>>                         >
>>                         > This used to work. In an older wiki I've
>>        built I
>>               have exactly
>>                         the same
>>                         > definitions and it works. I get a drop down
>>        list
>>               of the image
>>                         strings
>>                         > and the selected image is displayed
>>                         > correctly in the template.
>>                         >
>>                         > Any ideas?
>>                         >
>>                         > Thanks!
>>                         >
>>
>> ------------------------------------------------------------------------------
>>                         > Let Crystal Reports handle the reporting - Free
>>               Crystal
>>                      Reports
>>                         2008 30-Day
>>                         > trial. Simplify your report design,
>>        integration and
>>                      deployment -
>>                         and focus on
>>                         > what you do best, core application coding.
>>        Discover
>>                      what's new with
>>                         > Crystal Reports now.
>>         http://p.sf.net/sfu/bobj-july
>>                         > _______________________________________________
>>                         > Semediawiki-user mailing list
>>                         > Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>                      <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>>
>>                               <mailto:
>> Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>                      <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>>>
>>
>>                         >
>>
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>                         >
>>                         >
>>
>>
>>
>> ------------------------------------------------------------------------------
>>                         Let Crystal Reports handle the reporting - Free
>>               Crystal Reports
>>                         2008 30-Day
>>                         trial. Simplify your report design,
>>        integration and
>>                      deployment -
>>                         and focus on
>>                         what you do best, core application coding.
>>        Discover
>>               what's
>>                      new with
>>                         Crystal Reports now.
>>         http://p.sf.net/sfu/bobj-july
>>                         _______________________________________________
>>                         Semediawiki-user mailing list
>>                         Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>                      <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>>
>>                               <mailto:
>> Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>
>>                      <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>
>>               <mailto:Semediawiki-user@...
>>        <mailto:Semediawiki-user@...>>>>
>>
>>
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>>
>>
>>
>>
>>
>>
>>
>>
>>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user

[Neill Mitchell]

LOL, I've been using it so long I've kinda forgot bits ;) That
cheatsheet is very useful. It's the little forgotten bits that cause the
headaches!

Thanks Yaron.
Yaron Koren wrote:

> That's great! Let me take this opportunity to plug the SMW quick
> reference, AKA the SMW cheat sheet:
>  
> http://semantic-mediawiki.org/wiki/Image:SMW_quick_reference.pdf
>  
> $smwgLinksInValues is mentioned right in the first column; in addition
> to lots of other good stuff.
>  
> -Yaron
>
> On Thu, Nov 5, 2009 at 11:04 AM, Neill Mitchell <neill@...
> <mailto:neill@...>> wrote:
>
>     Aha! That sorts it out! Man, I have pored over the two
>     LocalSettings.php files for ages and must've missed it :) One more
>     item to go into my SMW tips and trips instance so I don't lose it
>     again!
>
>     It is always difficult to explain stuff like this. I was going to
>     suggest that you make the mods to my example to get us to a common
>     point, but now it's working anyway. Not a bug, which is good news
>     all round.
>
>     Now all I have to sort out is this MS Office file upload issue ;)
>
>     Thanks a lot for your patience Yaron.
>
>
>     Cheers
>     Neill.
>     Yaron Koren wrote:
>
>         Okay, I confess I don't quite understand the issue, but that
>         may be because you're experiencing two or three problems at
>         the same time... adding this to LocalSettings.php may help,
>         though:
>          $smwgLinksInValues = true;
>          -Yaron
>
>          On Thu, Nov 5, 2009 at 10:25 AM, Neill Mitchell
>         <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>>
>         wrote:
>
>            Hi Yaron.
>
>            But why can I no longer have
>            [[Image:Red]],[[Image:Amber]],[[Image:Green]] in the
>         property? Or
>            any [] characters in fact. You should be able to have any
>            characters in a string property. I know there are others
>         you can't
>            have either, :: for example. It completely trashes the
>         page. Which
>            is a real pain if you are running a SMW for a C++ development
>            group! ;) I have to tell my users to put a space between
>         the colons.
>
>            I think we are getting confused here. You suggested a work
>         around
>            to the issue of not being able to have [] characters in the
>            property as it causes a parsing error with SF. You suggested
>            moving the [] chars from the property definition to the
>         template
>            to get round the problem. I'm simply saying that your suggested
>            work around will display  [] characters if the string is empty.
>
>            Am I making sense?
>
>
>            Cheers
>            Neill.
>
>
>
>            Yaron Koren wrote:
>
>                I see. Well, that doesn't sound like a Semantic Forms
>         issue,
>                and it's probably not a Semantic MediaWiki issue
>         either... it
>                sounds like MediaWiki's own handling changed at some point.
>                You may have to use the #if function to solve it.
>                 -Yaron
>
>                On Thu, Nov 5, 2009 at 10:00 AM, Neill Mitchell
>                <neill@... <mailto:neill@...>
>         <mailto:neill@... <mailto:neill@...>>
>                <mailto:neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>>>
>                wrote:
>
>                   Hi Yaron.
>
>                   No, what I am saying is that if I move the
>         [[image:]] to the
>                   template to get round the property/form string
>         problem then the
>                   user will see [[image:]] if the property string is
>         empty. This
>                   isn't just images either. Normal links have the same
>         problem.
>
>                   If I have a string property "Link", for example and the
>                following:
>
>                   Form def:
>                   ! Article Link:
>                   | {{{field|ArticleLink|}}}
>                   |-
>
>                   Template def:
>                   ! Article Link
>                   | [[Link::{{{ArticleLink|}}}]]
>                   |}
>
>                   Then when the user puts in, say, [[MyPage]], what
>         you see
>                on the
>                   page is [[Link::MyPage]]
>
>                   If I were to move the [[]] to the template to solve this
>                problem
>                   as you originally suggested, you will see [[]]
>         displayed if no
>                   Link string was entered (quite legitimately) in the
>         form. This
>                   obviously looks wrong.
>
>                   You see my problem?  This used to all work fine.
>
>                   Cheers
>                   Neill.
>                   Yaron Koren wrote:
>
>                       Sorry, is the problem what appears on the page
>         itself?
>                If so,
>                       it's not a Semantic Forms problem... if you're
>         just talking
>                       about not being able to point a property to an
>         image,
>                that's
>                       been an issue in SMW for a long time; the key is
>         to have a
>                       line like:
>                        [[Property::Image:ImageName| ]] [[Image:ImageName]]
>                        ...in other words, have separate calls for the
>                property and
>                       for the image display.
>                       -Yaron
>                       On Thu, Nov 5, 2009 at 4:19 AM, Neill Mitchell
>                       <neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>
>                <mailto:neill@...
>         <mailto:neill@...> <mailto:neill@...
>         <mailto:neill@...>>>
>                       <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>> <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>>>>
>                       wrote:
>
>                          Hi Yaron.
>
>                          Thanks for getting back to me.
>
>                          Unfortunately while this is fine for
>         mandatory fields, I
>                       also have
>                          other non mandatory string fields that hold
>         links.
>                So if I
>                       put the
>                          tagging into the template then it will always
>         show even
>                       when the
>                          string is empty.
>
>                          The version of SF where this is working okay is
>                1.7.8. Not
>                       sure if
>                          that is any help!
>
>                          Best regards
>                          Neill.
>                          Yaron Koren wrote:
>
>                              I think the issue is that the brackets in the
>                property
>                       value
>                              are messing up the property call somehow.
>         Whether or
>                       not this
>                              is a fixable bug, it looks like there's
>         an easy
>                workaround,
>                              which is to make the values for the property
>                just "Red",
>                              "Amber" and "Green" instead, and have the
>                template add
>                       on the
>                              image tag and the rest when it's displayed.
>
>                              -Yaron
>
>
>                              On Wed, Nov 4, 2009 at 11:07 AM, Neill
>         Mitchell
>                              <neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>> <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>>
>                       <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>> <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>>>
>                              <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>
>                       <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>> <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>
>                       <mailto:neill@...
>         <mailto:neill@...>
>                <mailto:neill@...
>         <mailto:neill@...>>>>>>
>
>                              wrote:
>
>                                 Just to clarify
>
>                                 [[RAG::Image:Red.png
>                                      
>         <http://localhost/agility/index.php/File:Red.png>]]
>
>                                 Shows as
>
>                                 [[RAG::Actual little red box image]]
>         if you
>                get what
>                       I mean.
>
>                                 :)
>
>                                 Neill Mitchell wrote:
>                                 > I've got SMW 1.4.3 MW 1.15.1 and SF
>         1.8.3.
>                I have the
>                              following
>                                 defined:
>                                 >
>                                 > A string property called RAG. I have
>         3 values
>                       defined for it:
>                                 >
>                      
>         [[Image:Red.png]],[[Image:Amber.png]],[[Image:Green.png]]
>                                 >
>                                 > In my template definition I have:
>                                 > ! RAG
>                                 > | [[RAG::{{{RedAmberGreen|}}}]]
>                                 > |-
>                                 >
>                                 > In my form definition I have:
>                                 > ! RAG:
>                                 > |
>                                        
>          {{{field|RedAmberGreen|restricted|default=[[Image:Red.png]]}}}
>                                 > |-
>                                 >
>                                 > Now, when I'm in the form to create
>         a page,
>                there
>                       is no
>                                 drop-down for
>                                 > the RAG field. I just get a string
>         field.
>                When I
>                       save the
>                              default is
>                                 > correctly saved. However it is
>         displayed in the
>                       template as:
>                                 > [[RAG::Image:Red.png
>                                      
>         <http://localhost/agility/index.php/File:Red.png>]]
>                                 > instead of just the red box image.
>                                 >
>                                 > So why no drop down list and why the
>                [[RAG:: ]] around
>                              the image?
>                                 >
>                                 > This used to work. In an older wiki I've
>                built I
>                       have exactly
>                                 the same
>                                 > definitions and it works. I get a
>         drop down
>                list
>                       of the image
>                                 strings
>                                 > and the selected image is displayed
>                                 > correctly in the template.
>                                 >
>                                 > Any ideas?
>                                 >
>                                 > Thanks!
>                                 >
>                                                  
>         ------------------------------------------------------------------------------
>                                 > Let Crystal Reports handle the
>         reporting - Free
>                       Crystal
>                              Reports
>                                 2008 30-Day
>                                 > trial. Simplify your report design,
>                integration and
>                              deployment -
>                                 and focus on
>                                 > what you do best, core application
>         coding.
>                Discover
>                              what's new with
>                                 > Crystal Reports now.
>                 http://p.sf.net/sfu/bobj-july
>                                 >
>         _______________________________________________
>                                 > Semediawiki-user mailing list
>                                 >
>         Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>                            
>          <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>>
>                                      
>         <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>                            
>          <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>>>
>
>                                 >
>                            
>         https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>                                 >
>                                 >
>
>
>                                                  
>         ------------------------------------------------------------------------------
>                                 Let Crystal Reports handle the
>         reporting - Free
>                       Crystal Reports
>                                 2008 30-Day
>                                 trial. Simplify your report design,
>                integration and
>                              deployment -
>                                 and focus on
>                                 what you do best, core application coding.
>                Discover
>                       what's
>                              new with
>                                 Crystal Reports now.
>                 http://p.sf.net/sfu/bobj-july
>                                
>         _______________________________________________
>                                 Semediawiki-user mailing list
>                                 Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>                            
>          <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>>
>                                      
>         <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>
>                            
>          <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>
>                       <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>
>                <mailto:Semediawiki-user@...
>         <mailto:Semediawiki-user@...>>>>>
>
>                                            
>         https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>
>
>
>
>
>
>
>
>
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@...
https://lists.sourceforge.net/lists/listinfo/semediawiki-user