Release 1.5, markup extension format support!

Coordinator
Feb 24, 2011 at 12:20 AM
Edited Feb 24, 2011 at 12:36 AM

XamlStyler has been though quite a long silence since last release, however, my life was not as silent.

There were quite a few significant life events happened in last a few month:

1. My new house decoration project was finished. After all what have been through, there is one thing I learnt, software projects are much much easier to be managed than construction projects...

2. I have found a new job, and will start my new career soon.

3. The most significant, my second son came into the world just in past a few days.

And this release were all coded during my son's feeding hours in the early morning (or late evening) while I was get "excited" up from the bed.

Hope coding under this condition won't bring too many regressions, although 1.5 has been through the updated unit tests.

However, still, thank you for all your patience and encouragements.

Wish you will enjoy the new release just like how I enjoyed my second son's birth.

Last but not least, please do let me know if there is any issue met in 1.5.

Thanks!

 

P.S,

Would you please do me a favor, that please spare your attention to rate this tool here and "http://visualstudiogallery.msdn.microsoft.com/en-us/d6634d0e-38fb-48b6-829f-dadbc5c2fb62", in order to get XamlStyler a higher rank in the search result? Thanks!!!

Coordinator
Feb 24, 2011 at 12:37 AM

Reply to put this thread on top.

Feb 25, 2011 at 8:22 AM

Hello Chris, 

Congrats for your new born baby, your new job and the house decoration. And you still got time to make a new release, so thanks a lot !!
I'm glad you could make it :-)

As you ask for feedback, here is some bugs I discovered in the new version (by priority descending ie. the first is the most important) :

  1.  When there is a binding with two }}, sometimes the last one is removed
  2.  When I beautify, the text become selected from my cursor, to the end of the file

Eg for 1. : 
<Setter x:Uid="Setter_75" Property="Foreground" Value="{DynamicResource {x:Static SystemColors.ControlTextBrushKey}}" />
became 
<Setter x:Uid="Setter_75" Property="Foreground" Value="{DynamicResource {x:Static SystemColors.ControlTextBrushKey}" />

Also, when you got some time, it would be great to have those wishes in a release :

  1. Style the MultiTrigger.Conditions as the Trigger (which is a nice functionnality by the way)
  2. Don't style comments, especially if it's xaml, because it become flat and can't be read anymore
  3. Don't go to the cursor after the xaml has been styled
  4. Don't style again, if the xaml is already styled, because that could take some time for big xaml, and also mark all as modified, even if it is not
  5. Give the possibility to change the shortcut (Ctrl+K, Ctrl+2 is great, but it could be difficult to remember)

But even without it, your piece of code is very usefull !! Thanks for making my code well organized :-)

F£ö

Coordinator
Feb 25, 2011 at 9:50 AM
thanks for the issue report, i will make a fix asap.

On 2/25/11, flodef <notifications@codeplex.com> wrote:
> From: flodef
>
> Hello Chris, Congrats for your new born baby, your new job and the house
> decoration. And you still got time to make a new release, so thanks a lot
> !!
> I'm glad you could make it :-)As you ask for feedback, here is some bugs I
> discovered in the new version (by priority descending ie. the first is the
> most important) : When there is a binding with two }}, sometimes the last
> one is removed When I beautify, the text become selected from my cursor, to
> the end of the fileEg for 1. :
> <Setter x:Uid="Setter_75" Property="Foreground" Value="{DynamicResource
> {x:Static SystemColors.ControlTextBrushKey}}" />
> became
> <Setter x:Uid="Setter_75" Property="Foreground" Value="{DynamicResource
> {x:Static SystemColors.ControlTextBrushKey}" />Also, when you got some time,
> it would be great to have those wishes in a release :Style the
> MultiTrigger.Conditions as the Trigger (which is a nice functionnality by
> the way)Don't style comments, especially if it's xaml, because it become
> flat and can't be read anymoreDon't go to the cursor after the xaml has been
> styledDon't style again, if the xaml is already styled, because that could
> take some time for big xaml, and also mark all as modified, even if it is
> notGive the possibility to change the shortcut (Ctrl+K, Ctrl+2 is great, but
> it could be difficult to remember)But even without it, your piece of code is
> very usefull !! Thanks for making my code well organized :-)F£ö
>
>

--
Sent from my mobile device
Coordinator
Feb 25, 2011 at 10:03 AM
Btw, there is a work around you may try.

The bug will be tiggered only when a mark extension is nested without
a "key=", if you add the "key=", the formatting should work correctly.

Sorry for the inconvinience.

On 2/25/11, flodef <notifications@codeplex.com> wrote:
> From: flodef
>
> Hello Chris, Congrats for your new born baby, your new job and the house
> decoration. And you still got time to make a new release, so thanks a lot
> !!
> I'm glad you could make it :-)As you ask for feedback, here is some bugs I
> discovered in the new version (by priority descending ie. the first is the
> most important) : When there is a binding with two }}, sometimes the last
> one is removed When I beautify, the text become selected from my cursor, to
> the end of the fileEg for 1. :
> <Setter x:Uid="Setter_75" Property="Foreground" Value="{DynamicResource
> {x:Static SystemColors.ControlTextBrushKey}}" />
> became
> <Setter x:Uid="Setter_75" Property="Foreground" Value="{DynamicResource
> {x:Static SystemColors.ControlTextBrushKey}" />Also, when you got some time,
> it would be great to have those wishes in a release :Style the
> MultiTrigger.Conditions as the Trigger (which is a nice functionnality by
> the way)Don't style comments, especially if it's xaml, because it become
> flat and can't be read anymoreDon't go to the cursor after the xaml has been
> styledDon't style again, if the xaml is already styled, because that could
> take some time for big xaml, and also mark all as modified, even if it is
> notGive the possibility to change the shortcut (Ctrl+K, Ctrl+2 is great, but
> it could be difficult to remember)But even without it, your piece of code is
> very usefull !! Thanks for making my code well organized :-)F£ö
>
>

--
Sent from my mobile device